Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 26, 2024

This PR contains the following updates:

Package Change Age Confidence
jest-react (source) 0.14.0 -> 0.16.0 age confidence
react (source) 18.2.0 -> 18.3.1 age confidence
react-test-renderer (source) 18.2.0 -> 18.3.1 age confidence

Release Notes

facebook/react (jest-react)

v0.16.0

Compare Source

v0.14.2

Compare Source

React DOM
  • Fixed bug with development build preventing events from firing in some versions of Internet Explorer & Edge
  • Fixed bug with development build when using es5-sham in older versions of Internet Explorer
  • Added support for integrity attribute
  • Fixed bug resulting in children prop being coerced to a string for custom elements, which was not the desired behavior
  • Moved react from dependencies to peerDependencies to match expectations and align with react-addons-* packages

v0.14.1

Compare Source

React
facebook/react (react)

v18.3.1

Compare Source

  • Export act from react f1338f

v18.3.0

Compare Source

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React
  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #​25383
  • Warn for deprecated defaultProps for function components #​25699
  • Warn when spreading key #​25697
  • Warn when using act from test-utils d4ea75
React DOM
  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #​28874

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Apr 26, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: reactive-graphql-react@0.0.0-development
npm error Found: jest@29.6.2
npm error node_modules/jest
npm error   dev jest@"29.6.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.2
npm error node_modules/jest-react
npm error   dev jest-react@"0.14.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-04-26T20_45_38_299Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-26T20_45_38_299Z-debug-0.log

@renovate
Copy link
Contributor Author

renovate bot commented Oct 30, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: reactive-graphql-react@0.0.0-development
npm error Found: react@18.3.1
npm error node_modules/react
npm error   dev react@"18.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^19.0.0" from jest-react@0.16.0
npm error node_modules/jest-react
npm error   dev jest-react@"0.16.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-21T23_37_21_497Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-21T23_37_21_497Z-debug-0.log

@renovate renovate bot force-pushed the renovate/react-monorepo branch from bbc218e to afbdc04 Compare October 30, 2024 05:02
@renovate renovate bot force-pushed the renovate/react-monorepo branch from afbdc04 to d3844af Compare December 5, 2024 18:25
@renovate renovate bot changed the title chore(deps): update react monorepo chore(deps): update react monorepo to v18.3.1 Dec 8, 2024
@renovate renovate bot changed the title chore(deps): update react monorepo to v18.3.1 chore(deps): update react monorepo Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant